﻿using Microsoft.VisualStudio.TestTools.UnitTesting;
using SmallBusinessKit.DataAccess.Infrastructure;
using SmallBusinessKit.DataAccess.Interfaces;

namespace SmallBusinessKit.Tests
{
    /// <summary>
    /// Base class for all unit tests
    /// </summary>
    /// <remarks>
    /// There are two schools of thought on unit-testing. One writes a test for every single
    /// Assert(). The other see nothing wrong with multiple Asserts in a single test
    /// because I'm testing a case as a whole. That and I don't get paid the number of tests
    /// or how long it takes to code and test ~ lol. Yes, some people actually do that...
    /// </remarks>
    [TestClass]
    public class UnitTestBase
    {
        #region Properties

        protected IXmlDataParser     XmlData;
        //protected IList<Person>      PersonList;
        //protected IList<News>        NewsList;
        //protected IList<Testimonial> TestimonialsList;
        
        #endregion Properties

        #region Tests

        [TestInitialize]
        public virtual void Setup()
        {
            XmlData = new XmlDataParser("Items.xml", "Items.xml", "People.xml", "News.xml", "Testimonials.xml");
        }

        [TestCleanup]
        public void TearDown()
        {
        }

        #endregion
    }
}
